feat: adding agentic audience proposal - #24
emilhlauritsenWT wants to merge 4 commits into
Conversation
|
Adding a README that explains how this intent is meant to be referenced/used beyond this MR would help. We still need to backfill READMEs for the other intents, but since we're introducing a new intent here, this is a good place to start: For example: ADD_CIDSAttaches user segments containing agentic audiences embeddings Payload: Eligible paths:
Payload fields:
Example mutation{
"intent": "ADD_DATA_SEGMENT_WITH_EMBEDDINGS",
"op": "OPERATION_ADD",
"path": "/user/data",
"data_segments": {
"data": [
{
"name": "data-provider",
"segment": [
{
"id": "seg-ctx-001",
"name": "descriptive-name",
"ext": {
"aa": {
"ver": "1.0.0",
"vector": "mpkZPq5HYb5SuJ4+PQrXPo/C9T7NzEy97FE4Pilcj74=",
"dimension": 8,
"model": "sbert-mini-ctx-001",
"type": [2]
}
}
}
]
}
]
}
} |
86c9c31 to
ec63c4b
Compare
|
The PR description still says ADD_DATA_SEGMENT_WITH_EMBEDDINGS and data_segments = 105, but the proto adds ADD_EMBEDDINGS = 9 and reuses content_data. Could you update the description? It currently describes a different wire change. |
Updated |
3 participants
SUPPORTING DOC: ARTF A.A. ADD_EMBEDDINGS
Summary
This PR proposes a new
ADD_EMBEDDINGSintent so an ARTF agent can attach OpenRTB user data segments that carry Agentic Audiences embeddings (segment[].ext.aa) to a bid request.It does not invent a new bidstream carrier or a new ARTF payload type. It reuses:
DataPayloadviaMutation.content_data(content_data = 104)BidRequest.user.data[].segment[].ext.aaEmbeddings are required for this intent (
ext.aamust be present on each segment).This is a strictly additive schema extension:
Intent.ADD_EMBEDDINGS = 9DataPayload content_data = 104(no new payload field)Hosts and agents that do not use embeddings are unaffected. Experimental reserved ranges (
1000–1999) are untouched.Dependency: OpenRTB protobuf
Segment.ext.aa— openrtb2.x#188.Changes
proto/agenticrtbframework.proto— addsADD_EMBEDDINGS = 9; reusescontent_data/DataPayloaddocs/00-EXAMPLE.md— intent table, mapping, and example mutationdocs/intents/add-embeddings.md— intent usage guideExample
{ "intent": "ADD_EMBEDDINGS", "op": "OPERATION_ADD", "path": "/user/data", "content_data": { "data": [ { "name": "data-provider", "segment": [ { "id": "seg-ctx-001", "name": "descriptive-name", "ext": { "aa": { "ver": "1.0.0", "vector": "mpkZPq5HYb5SuJ4+PQrXPo/C9T7NzEy97FE4Pilcj74=", "dimension": 8, "model": "sbert-mini-ctx-001", "type": [2] } } } ] } ] } }